home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Cream of the Crop 26
/
Cream of the Crop 26.iso
/
program
/
p063b9s.zip
/
HELP
/
MAILSCAN.TXT
< prev
next >
Wrap
Text File
|
1993-12-29
|
11KB
|
298 lines
;╔══════════════════════════════════════════════════════════════════════════╗
;║ Helpfile for Portal of Power Last changed: 29.12.93 DW ║
;║ ║
;║ (C) Copyright 1989-93 by ║
;║ Dan Wulff, Jens Sandalgaard, Steen Christensen & S¢ren Ager ║
;║ ║
;║ This file may not be given to anybody, without the written permission ║
;║ from The Portal Team. ║
;╚══════════════════════════════════════════════════════════════════════════╝
;
;
;===========================================================
; MAIL SCANNER / NETMAIL
;-----------------------------------------------------------
!TOPIC 220 Netmail dir
!NOINDEX
This entry must point to your netmail/matrix directory. It is used for various
tasks, performed by Portal, including the operation of PortalFix, reposting
messages to your 3D points, and the operation of the mail scanner (future).
;
;-----------------------------------------------------------
!TOPIC 221 Strip crash
!NOINDEX
If you set this option to Yes, Portal will strip the Crash bit, from any
forwarded net mail.
;
;-----------------------------------------------------------
!TOPIC 222 Set AKA sent
!NOINDEX
Not described yet!
;
;-----------------------------------------------------------
!TOPIC 223 Save fwd mail
!NOINDEX
If you set this option to Yes, Portal will strip the kill/sent bit from any
forwarded message. If it is set to No, Portal will add the kill/sent bit
instead.
;
;-----------------------------------------------------------
!TOPIC 224 Forward mail
!NOINDEX
If you set this option to Yes, Portal will readdress any net mail messages,
which are addressed to one of your points, to their 3D address instead of
their 4D address, since you mail scanner/tosser/router did not handle it.
;
;-----------------------------------------------------------
!TOPIC 225 Kill fwd files
!NOINDEX
Whenever Portal is forwarding a net mail, with a file attach, to one of your
points, this option controls if the file should be deleted or not, once it has
been sent. If you set it to Yes, Portal will delete the file when it has been
picked up, otherwise it will leave it alone.
;
;-----------------------------------------------------------
!TOPIC 226 Hudson netmail
!NOINDEX
This entry is used to tell Portal which folder number is your net mail folder,
in your Hudson style message base. If you specify the correct number here, the
mail scanner will import all messages that is addressed to your system, from
the net mail directory, into this folder number.
;
;===========================================================
; MAIL SCANNER / ECHOMAIL
;-----------------------------------------------------------
!TOPIC 240 Save dupes dir
!NOINDEX
This entry should point to a directory, where Portal should put any dupes
that are detected, while tossing inbound mail. If it is left empty, the dupes
will simply disappear. If you want to limit the number of dupes that are kept
here, you may specify the maximum number in 241MailScan:EchoMail:Max dupes.
;
;===========================================================
!TOPIC 241 Max dupes
!NOINDEX
The maximum number of dupes to keep, is specified here. If you want to keep all
dupes, just specify a zero. If you specify anything but a zero, Portal will keep
a maximum of that number of dupes, and delete the first dupe in the
240MailScan:EchoMail:Save dupes-directory, to make room for any further dupes.
;
;===========================================================
!TOPIC 242 Echo Toss log
!NOINDEX
The Echo Toss log is created when echo mail is received. It is a plain ASCII text
file, containing the echo tag for any areas that mail is tossed into. The file
may be used to perform reply linking, and various other things, and should be
deleted once your system is through using it.
;
;===========================================================
; MAIL SCANNER / REMAPPER
;-----------------------------------------------------------
!TOPIC 260 ???
!NOINDEX
Not described yet!
;
;===========================================================
; MAIL SCANNER / SCHEDULES
;-----------------------------------------------------------
!TOPIC 280 Schedule number
!NOINDEX
Here you specify the schedule number, where this entry is to be used.
All schedule entryes with the same schedule number will be used during any
event specifying that Schedule number. In addition, all Scheduler entries
with the Schedule number Zero will always be executed. An example:
1) Event #1 just started.
2) You have specified 1 as Schedule number for this
event, in the Event Setup.
3) You have defined 3 Schedule entries for schedule #0,
and 2 for schedule #1.
So, during event #1, you'll have 5 active Schedule entries. And you'll have
at lease 3 active entries for any other events.
;
;-----------------------------------------------------------
!TOPIC 281 Action
!NOINDEX
This field defines what type of action you want this entry to do. There are 5
different actions, listed below. Use [+] / [-] or [Space] to select.
Poll Generate poll's for all nodes listed in
the 282Send to, with the 283Stat
specified.
Change Changes the stat of anything we have for the
nodes listed in 282Send to, to the 283Stat
specified.
Route Not used yet. It'll be active when the mail
scanner is ready.
Pack Not used yet. It'll be active when the mail
scanner is ready.
KillPoll Remove poll's, with the 283Stat specified
for all nodes listed in the 282Send to fields.
If you enter a space as the stat, ALL
poll's will be removed regardless of stat.
;
;-----------------------------------------------------------
!TOPIC 282 Send to
!NOINDEX
These two fields are used to specify the nodes that the 281Action is to
cover.
;
;-----------------------------------------------------------
!TOPIC 283 Stat
!NOINDEX
This field should contain one of the valid mail stats:
I Important
C Crash
D Direct
N Normal
H Hold
The only special case is the KillPoll action, which allows a space to be
specified.
See also: 281Action
;
;-----------------------------------------------------------
!TOPIC 284 Sub Line
!NOINDEX
The sub line number controls the order of the entries within each schedule.
Remember to sort the entries, by pressing F7 in the browser screen, when you
have changed any Sub Line numbers.
See also: 280Schedule number
;
;===========================================================
; MAIL SCANNER / MISC OPTIONS
;-----------------------------------------------------------
!TOPIC 320 ???
!NOINDEX
Not described yet!
;
;===========================================================
; MAIL SCANNER / CONFERENCES
;-----------------------------------------------------------
!TOPIC 300 Echo names
!NOINDEX
Each conference is identified by an echo mail tag, which is entered here.
;
;===========================================================
!TOPIC 301 Directory
!NOINDEX
Depending on what BBS-type you have specified, this entry contains different
information.
For *.MSG (Opus style) areas, the directory is specified.
For Hudson (QBBS style) it contains the folder number. It may contain a path
in front of the folder number, if the message base is not in the default
directory, E.g. C:\MSGBASE\80 for a message base located in C:\MSGBASE\.
For Squish (Maximus) it contains the path and file name (without extension)
;
;===========================================================
!TOPIC 302 Origin
!NOINDEX
The origin line is not used by the mail scanner, but is ment for use by a
message editor.
;
;===========================================================
!TOPIC 303 Aka
!NOINDEX
This entry controls which AKA will be used in the header of messages in this
area. Use '+' & '-' to select, ord space bar to cycle. Press ENTER when done.
;
;===========================================================
!TOPIC 304 Description
!NOINDEX
The description is used in PortalFix, and may be used by message editors etc.
It should contain a brief description of the conference.
;
;===========================================================
!TOPIC 305 Send to
!NOINDEX
This entry contains the receivers of the conference, which are allowed to send
messages into the area too. If you want to prevent a system from sending
messages, but still be able to receive messages, just enter the address in the
306Send ONLY-field instead.
;
;===========================================================
!TOPIC 306 Send ONLY
!NOINDEX
If a node is only to receive, and *NOT* be able to send messages in this
conference, enter the address here, otherwise put the receiver in the
305Send to-field.
;
;===========================================================
!TOPIC 310 Import SEEN-BY's
!NOINDEX
If you want to have seen-by lines preserved in messages that are put into your
message areas, set this option to 'Y' else set it to 'N'. If seen-by's are
imported, they will be hidden by putting an ASCII 1 in front of each line.
;
;===========================================================
!TOPIC 311 Level
!NOINDEX
The security level is used by PortalFix, to determine if the remote user has
access to the conference.
See also: 312Keys
;
;===========================================================
!TOPIC 312 Keys
!NOINDEX
The keys are used by PortalFix, to determine if the remote user has
access to the conference.
See also: 311Level
;
;===========================================================
!TOPIC 313 Max. Scan
!NOINDEX
If you leave this entry at zero, there will be no limit to the number of
messages scanned through the sysetem each day. Any other number will have the
effect that if you e.g. set it to 100, and receive 150 messages in this area,
only the first 100 messages are sent on, and the rest are tossed into the Bad
mail area, from which they will be taken before anything else the next day.
This is especially useful, if the conference trafic is received in big chunks
every 2-3 days, or something like that.
Be very careful when using this feature, since setting it too low might result
in a vast number of messages in your bad mail dir.
The Scanned field contains the message count, and Scan date contains the
last date that messages were processed in this area.